I just checked both !uld (zip local Airio files and send them to a defined FTP server), and !dld (copy all Airio.*.txt files from that remote FTP to Airio local folder). It works for me, when I saved a changed Airio.cfg.txt file to the external FTP server and typed !dld, in a minute the file was correctly stored under Airio, changes ready to be applied by !rld. Note that often you have direct FTP access to Airio folder (such as at 500servers), and in that case no !dld and !uld is necessary, you just upload changed files and then type !rld in game.
IdenKey option 1 will surely work, option 2 probably also. Concerning !dld, it should work as I described, it will move all Airio.*.txt files to the remote Airio folder. But it is long time since I've been using this function...
No, there is no such command. The best way is to look at the champions before erasing all champ data.
If I remember correctly, the !dld command takes all *.txt files from the set FTP server and transfers them to local Airio folder, overwriting existing TXT files. Then you can apply all changed settings by typing !rld on server.
Basically, everything is wrong. Ranks must be ascending (low to high), so you need to change order of rank texts and rank points. The same goes for safety ratings, low to high. But 101 is a number without any meaning, it means safety of 1.01%, Much better numbers would be 4000, 5000, 6000 (40, 50, 60%). The license time you have set means that anyone with lap time worse than WR + 1.2% will have no license, anyone with better server lap time will be SPEJSAJT, whatever that means. Again, reasonable numbers would be 200, 100, 50 (WR + 2, 1, 0.5%). Important is to always have the same number of numbers and texts in the pairs, or errors will happen.
New Airio version is released, you can read about all changes/additions in the detailed changelog. Some people may be concerned about the announced limitations, especially concerning the number of connected demo servers and their setup. Please note that these limitations are very benevolent (max. 7 demo servers, max. 3 of them for very low lap count), and also NOT active at present at the Airio Master server. They were implemented to try to fight some bad tendencies in demo racing, but since we have agreed with all concerned demo lovers and Airio admins on these limitations, they do not (I hope) need to be enforced. There are no plans to limit S1 and S2 servers in any way, except possibly limiting the total number of connected servers to one Airio PROS license to 10. Airio FULL/PROS owners will today in the evening receive the usual announcement post (if you need the new version sooner, contact me using MSN), again mentioning the prepared limitations. Note however, that at present they do not affect anyone.
Try actually entering the pitlane, after you cut the pit entry lines. Also give it a few seconds. Wrong pitlane entry can be detected only when you actually reach the pitlane (slow-down point) and you're seen in the pitlane, which takes some time...
@ Samix : Yes, the details will be published as soon as version 2.5.3 is ready to be released, but currently there is no Airio that would not comply with the "limitations".
It is a problem that started yesterday afternoon with many Airio instances. AA also cannot connect to airio.eu, all requests failing. FM too, AMG as well. It seems CG is currently the only popular Airio that can still connect. I'm trying to resolve the issue with my provider.
Yesterday some strange problems with airio.eu communication started. Requests from some Airios are completely ignored, while other requests work. I'm in contact with the site provider, but so far we can't spot the cause. Also the provider says that AIRW is putting too much load on their server, forcing me to move to higher and more expensive services, which I really cannot do. Anybody here knowing reliable, established, and cheap ASP.NET + SQL Server + domain provider?
Yeah, sorry, I just recently noticed that I forgot to update the item name. For CheckPitExit in SRV a corresponding PitExitNode in TCD is required. For CheckPitEntry in SRV you need to have a corresponding PitEntryNode in TCD. The TCD settings in essence say what is the last node you can be seen on proper racing path when entering pitlane, and what is the first node you can be seen on proper racing path when leaving pitlane.
I know the "limitations" word sounds bad. But please do see that they will in fact apply only in extreme demo cases, in just one or two cases for current Airios/servers, and the admins of those Airios are aware of this intention and accepting the reasons behind this move. Also, I do not plan to limit S2 servers in any way, except the total number of connected servers, probably to 10. Taking into account the private servers is an interesting idea. (Dave, does Nelson need more than 10 servers?) The problem is reaching this info - it is not so easy, it will probably have to go through the airio.eu site, which reads LFSW data about servers and knows their demo/private/laps status (as displayed on the servers overview page). These data are relatively extensive and reading/parsing them locally is not good. I had it once that way, but it did not work well.
Hehe, not faulty. Airio stopped, closed at that command. The TC panel saw a service (Airio) stopped, and restarted it. The solution is use StopExit=true in the CFG file. Airio will then disconnect from all servers after !quit, close stats etc., but it will stay running in a suspended state. And that means the panel will not restart it as a service; you have to kill it yourself later...
I guess the 81.19.209.205 was moved already? Sadly, we're experiencing unacceptable lags, all cars disappearing for like 2 seconds, for all connections at the same time. Also generally lagging is worse now than it was on the previous machine, resulting in heavy crashes for small touches. It is bad for the servers.
You should be always able to stop Airio using the !quit admin command...
Ye, Boothy, quite valid concern. I guess I'll have to create something and stick by it. Note that the limitations I intend to implement influence only demo servers. Layouts are not possible in demo. The only limit I'm considering for S1/2 servers is the total number connectable servers, maximum like 8, 9, or 10. And I'm not sure that would be a concern, except in very special cases.
I'm sure some of you have noticed some heated posts here, exchanges between me and Samix of the MRc team. This was caused by some Samix's moves concerning demo servers, which I considered very bad for the LFS, specifically running relatively large number of demo servers with the lowest requirements and standards, exploiting, in my view, the less important Airio functions, such as points and various ranks. We went through several stages of suggestions/refusal/request/acceptance, but in the end I felt cheated, with my tool used to bring LFS to an early death.
It now seems we have found a solution acceptable to both parties, and I would also hope a solution both preventing such excesses in the future and affecting Airio admins/owners only in very special cases. Airio 2.5.3 and newer will contain some hard-coded limitations. These limitations will try to make sure the tool applies reasonable and fair use principles. Just like there's fair driving style, when you give room to other cars, there should be a fair admining style, when you give room to other servers and admins. There are people going the popular way, and people trying to improve racing standards, especially in demo. Both should have their chance.
I have some limitations in mind quite clear. Maximum 6 demo servers connected to one Airio PROS, maximum 3 of them with very low lap count (3 and less), one for each demo combo. This should give enough breathing room, but at the same time leave room to other people with their servers. Also I would like to limit total maximum number of servers connected to one Airio PROS to 8 (FULL, just as FREE is already limited to 4). Or maybe 9 or 10, I'm not sure.
Well, your comments and ideas are welcome. The point is to limit certain possible excesses and unfair Airio use. This is an interesting and maybe controversial thing. If you see some catches or negative sides, please voice them now.
Well, that would surely be a good thing, nice idea. However, it needs implementation, both in Airio, in the AIRW database, as well as in the display page. Currently the server name is not send and is not known. I will attempt to add this functionality to Airio 2.5.3.
I do not want anything from you anymore. Through lengthy explanations I was looking for understanding and until today I thought we reached it. But then I realized how wrong I was. Go your own way, but not using my tool.
I explained this all to you about 5 times already, about 3 times you seemed to understand and about 4 times in the end ignored everything. Of course you can do whatever you want. Just please stay away from Airio in your attempts to improve LFS. This tool is not good enough for such a task. Thank you.
I will not live to see my tool being used to kill any remaining good racing in LFS. One day we make an agreement, the next day you break it, perfectly aware of what that means. You cheat, and I do not want cheater's money, so I sent them back.
Hm, I have to say that your rotation string looks OK.
Yes, that is true. LFS server may sometimes ignore all commands, if waiting for some new connection. Airio is checking conduct of all important commands, such as /spec, /kick, /ban, /restart, sending them repeatedly until executed, but this is not the case with other commands, so they can be really ignored. Eh, hard to solve this...
@ static : Ehm, yes, I see, but a server with 24 hour rotation is, I think, static. But again, I repeat, this is an attempt to create a server acceptable to vast majority of people and run by multiple teams. What I say and think has in no way any greater weight than what other team leaders think and want. If the majority wants 24 hour rotation, so be it. But so far it does not seem to be the case.
@ KY3 : Ah, yes. The server config was done initially for the GT racing, including GTL and GRT cars, so even longer tracks such as KY3 are rotated. But I guess if the server stays GTI+TBO, then some shorter tracks could be used as well, for example FE4 replaced by FE1, and SO1 also used...
@ goerge : Very nice analysis! It is for me hard to comment on all the mentioned things. Web stats, pages, announcements, subscriptions, all that would be great, but is there someone willing to do it? If so, raise your voice now! I can add some functionality to Airio supporting what would be needed, but I cannot do such pages.
This means, if somebody did not appear (more specifically, did not finish a single lap) in 600 days, then completely remove his stats. I'm usually using 300, so if someone leaves LFS for 10 months, he/she is forgotten.
I believe after qual the starting order is always based on qual times, only in subsequent races the LFS-specified order applies. For this you do not need Airio custom grid sorting, only standard LFS server settings.
Yes, see these items in SRV:
# Make sure cars coming from pits observe the lines - boolean # This has to be accompanied by valid PitExitNode item in TCD file. CheckPitExit=true
# What penalty to apply in case of bad pit exit in race - string # Possible values are 30 (seconds), 45 (seconds), dt (drive through), # sg (stop and go), pl (pitlane), sc (spectate), or empty (no penalty). PitExitPenalty=dt
Note the link to the PitExitNode item in TCD file. These items are not so easy to set correctly, but here's an example for BL1:
Track=BL1 PitExitNode=24
Also you must have the PTH files installed.
Rotation bugs are always (uhm) user errors, something wrong in the rotation format. In fact, the same can be said about most other bugs I receive and problems I solve.